AoAD2 Practice: Zero Friction
摩擦（friction）ゼロ
1時間デプロイを可能にするのが、zero-friction development
One-Second Feedback
早く（1秒以内で）フィードバックが返ってくるのがZero friction
スクリプト群を用意する（後述）
set up a watch script that automatically checks your code when you make a change.
次第に、ビルドは2つ必要になる
Eventually, you’ll probably need to set up two builds: one for fast feedback and one for production deployment.
Know Your Editor
Take the time to get to know your editor really, really well.
エディタが思考を遮るのを防ぐ
ペアプロ・モブプロで起こる
VSCode調べてみたい
Reproducible Builds
どの時点のコミットに戻してもテストは通り、ビルドできる
a build that continues to work and pass its tests no matter which development machine you use to build it, and no matter how old the code you’re building is.
2つの要件
Dependency management
コードがどのマシンでも同じように動くことを保証
Dependency management ensures your code runs the same way on every machine,
Local builds
テストについてどのマシンでも同じように動くことを保証
Five-Minute Integration
Your script should report success or failure within five minutes—ten at most.
早期に失敗するように実装する（長いビルドを後回し）
it needs to validate the code and report success or failure, before performing longer-running checks.
Control Complexity
key idea: OPTIMIZE FOR MAINTENANCE
このコラムはしびれた
it’s much more important to decrease costs of maintenance than to make it easier to write new code.
choosing simple tools and libraries that are easy to understand, easy to compose, and easy to replace
It’s more important to optimize maintenance costs than initial development,
think about the maintenance burden the dependency will add, and how well it will play with your existing systems.
積ん読